Verify azure attestation locally - not using MAA API#42
Merged
ameba23 merged 4 commits intopeg/add-maafrom Nov 26, 2025
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This targets #19 - not main
I was imagining we do an azure attestation by hitting the MAA api with a quote and HCL runtime data, and getting a JWT token from microsoft, which the verifier checks the signature of.
But now i understand the attestation code in
cvm-reverse-proxya bit better, i realize thats not what we are doing - we are verifying everything ourselves.This adds a similar attestation flow here - but does not yet have the vTPM certificate verification from flashbots/cvm-reverse-proxy#47